Skip to contentSkip to conversation

Support for NVMe-MI?

DISCUSSION Tony Lee (李文富) 2 participants 2 messages Feb 22, 2019 – Feb 26, 2019

lore
Share & tools
lore
#0 lore raw

Hi,

https://github.com/openbmc/openbmc/issues/3482 is asking support for NVMe-MI.

Now, we found that Google has a package called “google-ipmi-i2c”. It provides a ipmi bridge command which can get the device data where are on the i2c bus.

There are the command and response example below:

$ ipmitool -I dbus raw 0x2e 2 0x79 0x2b 0x00 14 0 0xd4 0 1 0 0xd5 0 8
response: 79 2b 00 06 bb ff 2a 00 00 00 2e
$ ipmitool -I dbus raw 0x2e 2 0x79 0x2b 0x00 14 0 0xd4 0 1 8 0xd5 0 24
response : 79 2b 00 16 80 86 50 48 4c 46 37 31 31 35 30 30
Response is define in NVM Express Management Interface SPEC
It's only used for in-band now.

How about adding support for out-of-band for this useful OEM command?

Thanks
Best Regards,
Tony

#1 lore raw

I expect you will be able to use the same command out-of-band if you add the relevant parameters to ipmitool to use the LAN. Can you report back if that isn't working for you?

Quoted 39 lines · Tony Lee (李文富)

Hi,

https://github.com/openbmc/openbmc/issues/3482 is asking support for NVMe-MI.

Now, we found that Google has a package called “google-ipmi-i2c”. It provides a ipmi bridge command which can get the device data where are on the i2c bus.

There are the command and response example below:

$ ipmitool -I dbus raw 0x2e 2 0x79 0x2b 0x00 14 0 0xd4 0 1 0 0xd5 0 8
response: 79 2b 00 06 bb ff 2a 00 00 00 2e
$ ipmitool -I dbus raw 0x2e 2 0x79 0x2b 0x00 14 0 0xd4 0 1 8 0xd5 0 24
response : 79 2b 00 16 80 86 50 48 4c 46 37 31 31 35 30 30

Response is define in NVM Express Management Interface SPEC

It's only used for in-band now.

How about adding support for out-of-band for this useful OEM command?

Thanks

Best Regards,

Tony